$ (cd code/python && \
    uv init --bare \
            --name keyring-insecure-backend \
            --package \
            --python 3.10)

+ add file header, order sections alphabetically, replace " by ',
  add classifiers, description, license; reset version to 0.0.0
+ NOTE: attempting to create a venv at this stage fails with
  $ (cd code/python && uv sync)
      ... (python exception leaked by uv omitted) ...
  ValueError: Unable to determine which files to ship
  inside the wheel using the following heuristics:
  https://hatch.pypa.io/latest/plugins/ ...
   ... builder/wheel/#default-file-selection

  The most likely cause of this is that there is no directory that
  matches the name of your project (keyring_insecure_backend).

  At least one file selection option must be defined
  in the `tool.hatch.build.targets.wheel` table,
  see: https://hatch.pypa.io/latest/config/build/

  As an example, if you intend to ship a directory named `foo` that
  resides within a `src` directory located at the root of your project,
  you can define the following:

  [tool.hatch.build.targets.wheel]
  packages = ["src/foo"]

  hint: This usually indicates a problem
  with the package or the build environment.

$ (cd code/python && \
     mkdir keyring_insecure_backend && cd $_ && touch __init__.py)

Resolved 15 packages in 304ms
      Built keyring-insecure-backend @ file:/// [...]
       ... keyring-insecure-backend/code/python
Prepared 6 packages in 570ms
Uninstalled 1 package in 1ms
Installed 6 packages in 4ms
 + jaraco-classes==3.4.0
 + jaraco-context==6.0.1
 + jaraco-functools==4.1.0
 + keyring==25.6.0
 ~ keyring-insecure-backend==0.0.0 (from file:/// [...]
    ... keyring-insecure-backend/code/python)
 + more-itertools==10.6.0

Resolved 16 packages in 385ms
      Built keyring-insecure-backend @ file:/// [...]
       ... keyring-insecure-backend/code/python
Prepared 2 packages in 1.18s
Uninstalled 1 package in 2ms
Installed 2 packages in 3ms
 ~ keyring-insecure-backend==0.0.0 (from file:/// [...]
    ... keyring-insecure-backend/code/python)
 + ruff==0.9.10

$ (cd code/python && uv remove --group dev ruff)
    ...

use in own conf file model; add conf: works but logs to stdout, not file

then process handler confs, finally call dictConfig(...) with the result

init members to None so they always exist and to list them all;
move secrets setup to own method; rename _data_dict to _secrets;
verify there is at least one logger conf'd, use first if more than one

make this the lead doc: first alphabetically --> likely first looked at

fails with `error: No files found to publish` (presumably) because
artifacts / package was built in build workflow, is not available here